Change Licenses and Options

Programming

System License and Option Selection

To change license options on the local system:

1. Go to the License and Option Selection form.

2. Select the System License and Option Selection tab.

3. Click Change.

5. Allocate licenses to the Licensed Options.

NOTE: The Available for Allocation field specifies the number of licenses that have been purchased, minus any licenses that have already been allocated. If license sharing is enabled, this is the total number available for all members of the application group. Otherwise, it is the number available for the local system only.

6. Enter the Configuration Options (e.g. Country, Maximum Configurable IP Users and Devices).

7. Click Save to commit your changes to the database and to the AMC.

Changes may require a Save/Reboot/Restore or a Reboot (see the table below), during which Voice Mail service may be interrupted for a few minutes.

NOTES

• When the system reboots, all service will be lost for approximately 20 minutes. To limit the impact of service disruption, reboot during a period of low traffic.

• Refer to the License and Option Selection form help for additional conditions that may apply to a license or option change.

• When the System Type is changed from "Standalone" to "Enterprise" in the AMC, the administrator must perform a backup and restore to ensure the integrity of the database.

• If you changed the number of locally allocated IP User or Multi-device User licenses, perform a database backup after the Save to avoid potential licensing issues after the database restore (see Reboot/Restore Requirements, Note 2).

• Switching System Type from"Enterprise" to "Standalone" in the AMC is not allowed. Even so, AMC will accept the change and record the hardware ID of the system against the Standalone ARID. This makes it impossible to retrieve licenses using the Enterprise ARID (which is still the valid ARID for that system) until the hardware ID of the Standalone ARID is cleared in the AMC.

 

CAUTION: Do not attempt to restore a database that has a greater number of telephone directory entries into a system that has been re-dimensioned with a smaller number of available directory entries. For example, you could set the Maximum Number of Cluster Elements to 250, flex and configure up to 65000 telephony directory entries, and save the database. Then, if you changed the Maximum Number of Cluster Elements in the License and Option Selection form from 250 back to 30 or 60 elements, the dimension for the Telephone Directory entries would be reduced to 20000 entries. After changing the dimension, you must not attempt to restore the large database into the smaller dimension. The data restore could take several hours to discard the extra entries and in most cases, the controller will reset before the restore is complete.

It is possible to change the Maximum Number of Cluster Elements from a high number to a lower number or to flex the dimension maximums down if you do not have greater than 20,000 entries programmed in Telephone Directory. However, if you have more than 20,000 entries, you will receive error messages during the restore (from DIM 19 to DIM 17) similar to the ones shown here. These messages indicate that the data in these fields is NOT being restored.

Currently restoring: Telephone Directory
The following record(s) failed to restore. Correct via CDE.
No more room to add new numbers. System digit strings pool is full.
[ Earvin/6304020/** Bad Data **/** Bad Data **/** Bad Data **/ Estern/Ontario]
No more room to add new numbers. System digit strings pool is full.
[ Earvin/6304021/** Bad Data **/** Bad Data **/** Bad Data **/ Estern/Ontario]|
No more room to add new numbers. System digit strings pool is full.
[ Earvin/6304022/** Bad Data **/** Bad Data **/** Bad Data **/ Estern/Ontario]
No more room to add new numbers. System digit strings pool is full.
[ Earvin/6304023/** Bad Data **/** Bad Data **/** Bad Data **/ Estern/Ontario]
No more room to add new numbers. System digit strings pool is full.
[ Earvin/6304024/** Bad Data **/** Bad Data **/** Bad Data **/ Estern/Ontario]
No more room to add new numbers. System digit strings pool is full.

These messages will appear regardless of whether data is programmed in the fields.

Application Group Licensing

To select the local system as the Designated License Manager for an application group:

1. Go to the Application Group Licensing form.

2. Click Change.

3. For Designated License Manager, select Yes.

4. Enter the Group Application Record ID (GARID) A value obtained from the Mitel Application Management Center (AMC). Used to license software on two or more MiVoice Business systems that are grouped into a single entity on the AMC for licensing purposes. and click Save.

5. Add the application group members to an SDS group and start sharing licensing data; for details see Start Sharing Licensing Data.

The local system becomes the Designated License Manager and application group licensing information is retrieved from the AMC. Application group licenses are pooled, enabling the group members share licenses subject to Core Package The minimum licensing required for every system that is sold and licensed through the Mitel Application Management Center. The Core Package tells the AMC what System Type to create on the Application Record and what licenses are included as part of the Core Package. It subsequently controls the type of licenses that can be added to the Application Record and what the license limitations (capabilities) of the Application Record are. Every Application Record on the AMC is essentially a Core Package with additional system licenses added on top of it. limits (Local Limits) and restrictions. Use the Application Group License Distribution form to track license usage.

See Application Group Licensing Example for more information on setting up license sharing.

To de-select the local system as the Designated License Manager for an application group:

1. Go to the Application Group Licensing form.

2. Click Change.

3. For Designated License Manager, select No.

4. Click Save.

The local system is de-selected as the Designated License Manager. You may now select another member of the application group serve as the DLM.

NOTE: Changes made in the Application Group Licensing form, or to the GARID on the AMC, must be followed by a SDS Sync from the Network Elements form on the DLM. For GARID changes, you must also retrieve the new GARID from the AMC before re-synchronizing by navigating to the Application Group Licensing form, and then clicking Change, followed by Save without actually changing anything.

Reboot/Restore Requirements

Option	Action		Automatic update
	Save/ Reboot/ Restore	Reboot immediately to update option
IP User Licenses			X (see Note 1 and Note 2)
External Hot Desk User Licenses			X
ACD Active Agent Licenses			X
HTML Apps Infrastructure Licenses			X
Single Line Users Licenses			X
Multi-Device Licenses			X (see Note 2)
Suite Licenses			X
Mailbox Licenses			X (see Note 3)
Voice Mail Hospitality/ PMS			X
Digital Link Licenses			X
Compression Licenses		X
Fax over IP (T.30) Licenses		X
SIP Trunk Licenses			X
Integrated Directory Service			X
Country	X
Extended Agent Skill Group	X
Maximum Elements per Cluster	X		(See Note 4)
Maximum Configurable IP Users and Devices	X
Extended Hunt Group	X
5560 IPT Device Extended Key Lines	X		(See Note 4)

NOTES

1. If you are installing a new system that does not have any IP User Licenses programmed, a reboot is required after you set the licenses for the first time. However, increases to the number of IP User Licenses are updated immediately without a reboot. If the Maximum Configurable IP Users and Devices is also modified, you must perform a system backup followed by a database restore.

2. Changing the number of locally allocated IP or Multi-device User Licenses can affect the results of restoring a database saved prior to the License and Option Selection form update. For example, if you reduce the number of IP User (IPU) Licenses to below the number consumed, the restored database will have some Multi-device User (MDU) Licenses consumed by Full Service IP users, causing some Multi-device User Groups (MdUG) to be thrown out due to lack of MDU licenses. Similarly, if you reduce the number of MDU Licenses, some Full Service IP users could be thrown out if they were consuming MDU licenses.

To avoid these issues, ensure that you back up the database after changing the number of locally allocated IPU or MDU, or both licenses.

3. A change in the number of Mailbox Licenses from zero to any value requires a Reboot.

4. Changing these options is a Dimension change, which results in the loss of all programmed data in the system database. To preserve the database, make a backup before changing the option. After the change and a reboot, restore the database using the Current Dimension Selections restore option.

IMPORTANT: Do NOT restore using the default "From archived file" restore option as this would restore the original database dimension.

5. The following options are enabled by default on all systems: Advanced Voice Mail, Tenanting, Remote Management, OIG/MiTAI Computer Integration.

6. The following options are enabled by default on Enterprise systems: IP Networking, Voicemail Networking, XNET Networking.

 

 

• Application Group Licensing Example

• License Violation Handling

• About IP User and Device Licenses

• Select Licenses and Options

• Change Resource Dimensions

• Replacing a DLM

• Removing an Application Group Member